Patch Tuesday "killed" IP printing
I got a call from a client 2010-Sep-16 that they could no longer print to either network printer from any workstation. All workstations have Vista Business 32 and were updated morning of Sep 16. Server is Server2003 & printing still worked fine from it. Printers were using IP ports fine for over 2 years. Fix was to create ports with full share name & use that instead of IP. The IP address of printer had not changed AND I could still browse with IE8 (using IP address) to printer to see config data of printer Workstations are in Server2003 domain. AV is McAfee Total Protection Service This full share name trick was how I previously had to set up Vista Home Premium workstations to use network printers in home networks. Why would Vista Business be "updated" to Home Premium settings? Is this a permanent "update"? Why does any version of VISTA do this? No workstations are Windows 7, so do not know if Win7 has same issue. With Vista Business 32 the (short term?) solution was to change the port to a local port with the full share name of the printer If this were to happen to the server, I think the fix will be unworkable unless the printer is directly attached to the server. I have no explanation as to why this has not happened to thousands of networks.
September 20th, 2010 5:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics